@mr-c FYI

Since the 1.2.1_proposed branch was merged, the $id does not resolve to the same URL as:
https://raw.githubusercontent.com/common-workflow-language/cwl-v1.2/v1.2.1/json-schema/cwl.yaml

This PR is targeting https://github.com/common-workflow-language/cwl-v1.2/tree/main, but a corresponding one would be needed for https://github.com/common-workflow-language/cwl-v1.2/tree/v1.2.1

Would that cause an issue in terms of tag override?

@mr-c FYI

Since the 1.2.1_proposed branch was merged, the $id does not resolve to the same URL as: https://raw.githubusercontent.com/common-workflow-language/cwl-v1.2/v1.2.1/json-schema/cwl.yaml

This PR is targeting https://github.com/common-workflow-language/cwl-v1.2/tree/main, but a corresponding one would be needed for https://github.com/common-workflow-language/cwl-v1.2/tree/v1.2.1

Would that cause an issue in terms of tag override?

I agree that each branch/tag needs a new commit updating the id field. However, since there will be no more changes to the syntax of CWL v1.2, maybe they should have the same value, like `https://w3id.org/cwl/v1.2/cwl-json-schema.yaml'?

Yes. That would work as well. Even better would be for that URI to also resolves/host the file, so it is somewhat more "official" than the GitHub location.